Deploying and configuring JBoss Enterprise Application Platform using the User Data field provides for flexibility and ease of management of multiple configurations. The flexibility comes from the use of various parameters which can be used to configure the platform or in the deployment of your custom application.
The following parameters can be used to influence the configuration and operation of JBoss Enterprise Application Platform. Their contents are written to /etc/sysconfig/jbossas and /etc/sysconfig/jon-agent-ec2.
|
NAME |
Description |
Default |
|
JBOSS_JGROUPS_S3_PING_ACCESS_KEY |
Amazon AWS user account access key for S3_PING discovery if clustering is used. |
N/A |
|
JBOSS_JGROUPS_S3_PING_SECRET_ACCESS_KEY |
Amazon AWS user account secret access key. |
N/A |
|
JBOSS_JGROUPS_S3_PING_BUCKET |
Amazon S3 bucket to be used for S3_PING discovery. |
N/A |
|
JBOSS_CLUSTER_ID |
ID of cluster member nodes. Only used for clustering. Accepted values are (in order):
|
last octet of eth0's IP address |
|
MOD_CLUSTER_PROXY_LIST |
Comma-delimited list of IPs/hostnames of mod_cluster proxies if mod_cluster is to be used. |
N/A |
|
PORTS_ALLOWED |
List of incoming ports to be allowed by firewall in addition to the default ones. |
N/A |
|
JBOSSAS_ADMIN_PASSWORD |
JBoss EAP password for "admin" user. |
N/A |
|
JON_SERVER_ADDR |
JON server hostname or IP with which to register. This is only used for registration, after that agent may communicate with other servers in the JON cluster. |
N/A |
|
JON_SERVER_PORT |
Port used by the agent to communicate with the server. |
7080 |
|
JON_AGENT_NAME |
Name of JON agent, must be unique. |
Instance's ID |
|
JON_AGENT_PORT |
Port that the agent listens on. |
16163 |
|
JON_AGENT_ADDR |
IP address to which the JON agent is to be bound. This is used when the server has more than one public address, e.g. VPN. |
agent chooses IP of local hostname by default |
|
JON_AGENT_OPTS |
Additional JON agent system properties which can be used for configuring SSL, NAT and other advanced settings. |
N/A |
|
JBOSSCONF |
Name of JBoss EAP profile to start. If S3 config is present, then cluster-ec2 profile is used. If MOD_CLUSTER_PROXY_LIST is specified, the mod_cluster-ec2 profile is selected me. If neither of these options are used then the 'default' profile is used. |
default, cluster-ec2 or mod_cluster-ec2 depending on the other parameters |
|
JAVA_OPTS |
Custom values to be added to the variable before JBoss Enterprise Application Platform starts. |
JAVA_OPTS is built from values of other parameters |
|
JBOSS_IP |
IP address to which server is to be bound. |
127.0.0.1 |
The following parameters can be used inside the user custom script part of user data.
|
JBOSS_DEPLOY_DIR |
Deploy directory of the active profile (e.g. /usr/lib/jbossas/server/cluster-ec2/conf) |
|
JBOSS_CONFIG_DIR |
Config directory of the active profile (e.g. /usr/lib/jbossas/server/cluster-ec2/conf) |
|
JBOSSCONF |
Name of EAP active profile |
|
USER_SCRIPT |
Path to the custom configuration script, which is available prior to sourcing user-data configuration |